Information processing system, information processing apparatus, and program

ABSTRACT

An information processing system sending setup information related to a setup of an apparatus to the apparatus includes the apparatus including a receiving unit configured to receive user information of a user of the apparatus, and a first communication unit configured to send the user information and the apparatus information related to the apparatus to an information processing apparatus, and the information processing apparatus including a second communication unit configured to receive the user information and the apparatus information, and a setup information determining unit configured to determine the setup information of the apparatus used by the user based on the apparatus information and the user information, wherein the second communication unit sends the setup information determined by the setup information determining unit to the apparatus.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates to an information processing system, aninformation processing apparatus, and a program.

2. Description of the Related Art

When a cloud server cooperates with various apparatuses, there is aneffect of improving convenience for a user or the like. For example, theapparatus such as a multifunction peripheral (a MFP) sends image dataobtained by scanning to a cloud server. Then, the cloud server isenabled to process the image data in conformity with a profile which ispreviously set (for example, a storage to an online storage).

A group such as a company or a department, which uses a resource of acloud serves, is called a tenant. The cloud server is used in units ofthe tenant. The apparatus is registered each tenant, and the registeredapparatus can use the resource of the cloud server. Meanwhile, the useroperating the apparatus is registered for each tenant. When the userlogs into the cloud server through the apparatus, the apparatusregistered in the cloud server can be used (step See, for example,Patent Document 1). Patent Document 1 discloses a cloud system, in whicha profile can be set for each user.

Patent Document 1: Japanese Laid-Open Patent Publication No. 2015-84516

In consideration of the above object, the present invention is toprovide an information processing system for providing appropriate setupinformation to the apparatus used by the user.

SUMMARY OF THE INVENTION

It is a general object of at least one embodiment of the presentinvention to provide an information processing system that substantiallyobviates one or more problems caused by the limitations anddisadvantages of the related art.

Provided is an information processing system sending setup informationrelated to a setup of an apparatus to the apparatus including theapparatus including a receiving unit configured to receive userinformation of a user of the apparatus, and a first communication unitconfigured to send the user information and the apparatus informationrelated to the apparatus to an information processing apparatus, and theinformation processing apparatus including a second communication unitconfigured to receive the user information and the apparatusinformation, and a setup information determining unit configured todetermine the setup information of the apparatus used by the user basedon the apparatus information and the user information, wherein thesecond communication unit sends the setup information determined by thesetup information determining unit to the apparatus.

Additional objects and advantages of the embodiments will be set forthin part in the description which follows, and in part will be clear fromthe description, or may be learned by practice of the invention. Objectsand advantages of the invention will be realized and attained by meansof the elements and combinations particularly pointed out in theappended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically illustrates an example of a relationship among atenant, a MFP as an example of an apparatus, and a user.

FIG. 2 illustrates an example of a relationship between the user and thetenant.

FIG. 3 illustrates an example of an outline of an information processingsystem of an embodiment.

FIG. 4 illustrates an example of an outline structure of the informationprocessing system.

FIG. 5 schematically illustrates an example of a schematic hardwarestructure of a cloud server.

FIG. 6 is an example of a block diagram schematically illustrating ahardware structure of the MFP.

FIG. 7A is an example of a functional block diagram for explainingfunction of the information processing system of the embodiment.

FIG. 7B illustrates an example of a data structure of a profile.

FIG. 8 is an example of a sequence diagram illustrating a login to thecloud server using a MFP of a tenant, in which oneself is notregistered, and the profile of oneself is used in the MFP.

FIG. 9 illustrates an example of an explanation of an app home screen orthe like.

FIG. 10 is an example of a flowchart for explaining a procedure ofdetermining a profile ID based on tenant information of the MFP andtenant information of the user.

FIG. 11 is an example of a sequence diagram illustrating a login to thecloud server using the MFP of the tenant, in which oneself is notregistered, and the profile of oneself is used in the MFP.

FIG. 12 an example of a functional block diagram for explaining thefunction of the information processing system.

FIG. 13 is an example of the sequence diagram illustrating the login tothe cloud server using the MFP of the tenant, in which the oneself isnot registered, and the profile of oneself is used in the MFP (stepSecond Embodiment).

FIG. 14 is an example of a flowchart illustrating a procedure that anapp determining unit limits an application (app) usable by the user.

FIG. 15 is an example of explaining a flow of an excluding process ofthe app using a use limitation.

FIG. 16 is an example of a functional block diagram for explaining thefunction of the information processing system.

FIG. 17 is an example of the sequence diagram illustrating the login tothe cloud server using the MFP of the tenant, in which the oneself isnot registered, and the profile of oneself is used in the MFP (ThirdEmbodiment).

FIGS. 18A to 18D are an example of explaining generation of a profiledifference.

FIG. 19 illustrates an example of a combined profile (V1.1.A).

FIG. 20 illustrates an example of explaining a profile after the logout.

FIGS. 21A and 21B are examples of a flowchart illustrating a procedurethat a profile processing unit processes a profile.

FIGS. 22A to 22C illustrate an example of explaining a screen transitionat a time of login.

FIG. 23 is an example of a functional block diagram for explaining thefunction of the information processing system (Fourth Embodiment).

FIG. 24 illustrates an example of a screen transition displayed by theMFP.

FIG. 25 is an example of the sequence diagram illustrating the login tothe cloud server using the MFP of the tenant, in which the oneself isnot registered, and the profile of oneself is used in the MFP (there isno same app).

FIG. 26 is an example of the sequence diagram illustrating the login tothe cloud server using the MFP of the tenant, in which the oneself isnot registered, and the profile of oneself is used in the MFP (there issame app).

FIG. 27 is an example of a flow chart for explaining a procedure that ascreen transition destination control unit determines a transitiondestination screen.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

A description is given below, with reference to the FIG. 1 through FIG.27 of embodiments of the present invention. Where the same referencesymbols are attached to the same parts, repeated description of theparts is omitted.

FIG. 1 schematically illustrates an example of a relationship among atenant, a multifunction peripheral (MFP) 10 as an example of anapparatus, and a user. In order to distinguish the multifunctionperipheral 10, multifunction peripherals 10 a and 10 b are illustrated.As illustrated, the MFPs 10 a and 10 b and the users 1 to 3 areregistered in the tenant. Description is given for the user 1. One ofthe effects exerted by a registration of the MFPs 10 a and 10 b is thatthe user can use the MFPs 10 a and 10 b by logging in a tenant fromeither one of the MFPs 10 a and 10 b and the user can use a profile 9such as a profile 1, which is ordinarily used by the user 1 from eitherone of the multifunction peripherals 10 a and 10 b. The profiles 1 to 3is setup information related to a setup of an operation of the MFP 10.In a case where the user 1 registers the profile 1 in a cloud server,regardless of whether the user 1 uses the multifunction peripheral 10 aor the multifunction peripheral 10 b, the multifunction peripheral 10 aor 10 b can be used by the same setup based on the profile 1.

However, in a case where a tenant, in which the MFP 10 is registered, isdifferent from a tenant, in which the user is registered, in aconventional cloud server, there is a problem that the user cannot usethe profile, which is ordinarily used. Referring to FIG. 2, descriptionis given. FIG. 2 illustrates an example of a relationship between theuser and the tenant. A tenant 111 and a tenant 222 are registered in acloud server 50. A MFP 10 a and the user 1 are registered in the tenant111. A MFP 10 b and the user 2 are registered in a tenant 222.

In a case where the user 1 logs into the cloud server 50 from the tenant111, the user 1 sets a profile 9 c ordinarily used by the user 1 to aMFP 10 a. Thus, the MFP 10 a becomes usable. Meanwhile, after the user 1logs into the cloud server 50 through the multifunction peripheral 10 bof the tenant 222, the user 1 is not registered in the tenant 222.Therefore, the user 1 cannot use the profile 9 c.

Embodiments of the present invention are explained with reference todrawings.

First Embodiment Outline of the Information Processing System of theFirst Embodiment

FIG. 3 illustrates an example of an outline of an information processingsystem 100 of the first embodiment. A user 1 is registered in a tenant111, into which a multifunction peripheral 10 a is registered. Further,the multifunction peripheral 10 a uses a profile 9 a as a profile of aninitial setup, and the user ordinarily uses a profile 9 c. In a casewhere the user 1 logs into a cloud server 50 through the multifunctionperipheral 1, a profile 9 c is set to the multifunction peripheral 10 aso that the multifunction peripheral 10 a can be used.

Described next is a case where the user 1 uses a multifunctionperipheral 10 b that is registered in a tenant 222.

(1) At first, the user 1 logs into the cloud server 50 through themultifunction peripheral 10 b. With this, the cloud server 50 specifiesthe multifunction peripheral 10 b and the user 1.

(2) The multifunction peripheral 10 b is registered in the tenant 222,and the user 1 is registered in the tenant 111. Therefore, the cloudserver 50 determines that the tenant, in which the user 1 is registered,differs from the tenant, in which the multifunction peripheral 10 b isregistered.(3) The cloud server 50 sends the profile 9 c of the user 1 registeredin tenant 111 to the multifunction peripheral 10 b under a predeterminedcondition. With this, the multifunction peripheral 10 b is operatedbased on the profile 9 c. Therefore, the user 1 can use themultifunction peripheral 10 b by using the same setup as that in usingthe multifunction peripheral 10 a installed in the tenant 111.

Terminology

For example, a resource recited in the claims corresponds to hardwareand software. For example, the resource recited in the claimscorresponds to a function provided by the hardware and the software.

For example, a group recited in the claims corresponds to a group ofpersons or matters, which have a common point common to the group. Forexample, when persons and/or things belonging to a certain company,business place, branch, department, affiliate company, class, room, orfloor, these persons and/or things belong to the same group. Within theembodiment, an apparatus and a user are registered using a unit ofgathering of the persons, for example. For example, the number of theperson or the thing belonging to the group nay be one. For example, agroup using a resource of the information processing system isconventionally called a tenant.

For example, the setup information relates to a setup of themultifunction peripheral. For example, according to the setupinformation, the multifunction peripheral is permitted or prohibited todo a possible operation. For example, the setup information may includeparameters of various processes performed by the multifunctionperipheral. For example, the setup information corresponds to a profilein the embodiments.

Example of System Structure

FIG. 4 illustrates an example of an outline structure of an informationprocessing system 100. The information processing system 100 includes acloud server 50 which is communicable through a network and multiplemultifunction peripherals 10 (when the multiple multifunctionperipherals are distinguished, the multiple multifunction peripherals 10a 1, 10 a 2, 10 b 1, and 10 b 2). The multifunction peripherals 10 maynot communicate each other. Here, “communicable” means that a functionof communicating between the cloud server 50 and the multiplemultifunction peripheral 10 is provided, and the communication may notbe actually performed between the cloud server 50 and the multiplemultifunction peripheral 10.

The multifunction peripherals 10 a 1 and 10 a 2 are located in a base 1.The multifunction peripherals 10 b 1 and 10 b 2 are located in a base 2.For example, in a case where the base 1 is a head office, the base 2 isa business place or a branch. Further, in a case where the base 1 is adepartment 1, the base 2 is a department 2. Furthermore, in a case wherethe base 1 is a company 1, the base 2 is a company 2 (a company closelyrelated to the company 1 such as an affiliate company). As such, aperson comes and goes between the base 1 and the base 2.

As an example, the multifunction peripherals 10 a 1 and 10 a 2 areregistered in the tenant 111 of the cloud server 50, and themultifunction peripherals 10 b 1 and 10 b 2 are registered in the tenant222 of the cloud server 50. However, it is sufficient to register atleast one multifunction peripheral 10 in each tenant. The exampleillustrated in FIG. 4 is only an example.

The multifunction peripheral 10 is an example of the apparatus recitedin the claims. The multifunction peripheral 10 includes a word “multi”,which represents multiple functions of printing, fax transmission,scanning of an original manuscript, copying, and so on. However, theapparatus may not have these multiple functions. It is sufficient forthe apparatus to have at least one function. The multifunctionperipheral 10 may be the apparatus called a multi-function peripheral(MFP), a copy machine, a copier, an image forming machine 10, or anoffice apparatus.

Further, the multifunction peripheral 10 may be replaced by a projector,a head up display (HUD), an electronic whiteboard, a digital signage, orthe like. Said differently, the apparatus of the embodiment may be anapparatus in which a user can use the profile 9.

The cloud server 50 is an example of the information processingapparatus. It is preferable that the cloud server can deal with cloudcomputing. Cloud computing is a mode of using the information processingapparatus, in which a resource on the network can be used withoutspecifically getting conscious of a hardware resource. In this case, thecloud server 50 may not be integrally provided as a single deviceaccommodated in a single casing. The cloud server 50 may be formed bydynamically connect or disconnect a hardware resource depending on aload. Further, the cloud server 50 may be built in a virtual environmentinside a single information processing apparatus or separatelystructured into multiple information processing apparatuses.

Although the cloud server 50 is provided in the Internet, the cloudserver may be provided in any place as long as the cloud server isconnected to the network. For example, the cloud server may exist in thebase 1 or the base 2.

A network N is built by a large area network (LAN) built in a base wherethe multifunction peripheral 10 is installed, a provider network of aprovider of connecting the LAN with the internet, a line served by atelecommunications carrier, or the like. In a case where the network Nincludes multiple LANs, the network N is called a wide area network(WAN) or the Internet. The network may be built so as to be wired orwireless or a combination of wired and wireless. In a case where themultifunction peripheral 10 has a function of connecting with a portablephone network such as 3G, long term evolution (LTE), and 4G, the networkN is the portable telephone network and a provider network.

Hardware Structure

FIG. 5 schematically illustrates an example of a schematic hardwarestructure of the cloud server 5. The cloud server 50 includes a centralprocessing unit (CPU) 201 and a memory 202 enabling a high speed accessto data used by the CPU 201. The CPU 201 and the memory 202 areconnected with another device or another driver in the cloud server 50through a system bus 203. The another device or another driver is, forexample, a graphics driver 204 or a network driver (NIC) 205.

The graphics driver 204 is connected to a liquid crystal display (LCD)(a display device) and monitors a processed result obtained by the CPU201. Further, the network driver 205 connects the cloud server 50 withthe network N at a transport layer and a physical layer to establish asession with the multifunction peripheral 10.

An input and output (I/O) bus bridge 207 is further connected with thesystem bus 203. On the downstream side of the I/O bus bridge, a memorydevice such as a hard disk drive (HDD) 290 is connected through an I/Obus using Integrated Drive Electronics (IDE), Advanced TechnologyAttachment (ATA), Advanced Technology Attachment Packet Interface(ATAPI), serial ATA, Small Computer System Interface (step SCSI),Universal Serial Bus (USB). The HDD 209 stores a program 209 p forcontrolling the entire cloud server 50. The HDD 209 may be a Solid StateDrive (step SSD).

Further, an input device 210 such as a keyboard and a mouse (called apointing device) is connected with the I/O bus 208 to receive an inputand a command by an operator such as a system administrator.

The hardware structure of the cloud server 50 illustrated in FIG. 5 maynot be integrated in a single casing. FIG. 5 illustrates hardwareelements preferably included in the cloud server 50. Further, a physicalstructure of the cloud server 50 of the embodiment may not be fixedlydeterminant in order to deal with cloud computing and may be built bydynamically connect or cut the hardware resource in response to theload.

[[Hardware Structure of the Multifunction Peripheral 10]]

FIG. 6 is an example of a block diagram schematically illustrating ahardware structure of the multifunction peripheral 10. The multifunctionperipheral 10 has a structure that a controller 410 and an engine part(Engine) 415 are connected using a Peripheral Component Interface (PCI)bus 416.

The controller 410 controls the entire multifunction peripheral 10,drawing, communicating, and an input from an operation panel 411. Theengine part 415 is a printer engine connectable to a PCI bus 416 or thelike. For example, the engine part 415 is a black and white plotter, a1-drum color plotter, a 4-drum color plotter, a scanner, or a facsimile(FAX) unit.

This engine part 415 includes an image processing part performing errordiffusion and gamma conversion in addition to the engine part such asthe plotter.

The controller 410 includes a CPU 401, a north bridge (NB) 403, a systemmemory (MEM-P) 402, a south bridge (step SB) 404, a local memory (MEM-C)407, an Application Specific Integrated Circuit (ASIC) 406, and a harddisk drive (HDD) 408. An Accelerated Graphics Port (AGP) 405 connectsthe NB 403 with the ASIC 406.

The MEM-P 402 further includes a Read Only Memory (ROM) 402 a and aRandom Access Memory (RAM) 402 b.

The CPU 401 performs an entire control of the multifunction peripheral10 and includes a chip set made up of the NB 403, the MEM-P 402, and theSB 404, and is connected with another apparatus through this chip set.

The NB 403 is a bridge for connecting the CPU 401, the MEM-P 402, the SB404, and the AGP bus 405, and includes a memory controller forcontrolling to read from and write into the MEM-P 402, a protocolcontrol information (PCI) master, and an AGP target.

The MEM-P 402 is a system memory used as a storing memory for storing aprogram and data, a deploying memory for deploying the programmed thedata, a drawing memory for drawing in the printer, or the like andincludes a ROM 402 a and a RAM 402 b.

The ROM 402 a is a read only memory used as a storing memory for storingthe program and the data. The RAM 402 b is a writeable and readablememory used as a deploying memory for deploying the program and the dataand a drawing memory for drawing in the printer.

The SB 404 is a bridge for connecting the NB 403, the PCI device, and aperipheral device. This SB 404 is connected with the NB 403 through thePCI bus. The network I/F 409 or the like is connected with the PCI bus.The ASIC 406 is an Integrated Circuit (IC) that includes the hardwareelement for the image processing and is provided for the purpose ofimage processing. The ASIC 406 plays a role of a bridge of mutuallyconnecting the AGP bus 405, the PCI bus 416, the HDD 408, and the MEM-C407.

This ASIC 406 includes a PCI target, an AGP master, an arbiter (ARB)that is a core of the ASIC 406, a memory controller for controlling theMEM-C 407, multiple Direct Memory Access Controllers (DMACs) forrotating the image data using a hardware logic and so on, and a PCI unitof transferring data through the PCI bus from and to the engine part415.

The network I/F 409 is a communication device for communicating with thecloud server 50 and so on through the network N. For example, thenetwork I/F 409 is a Network Interface Card (NIC).

A Facsimile Control Unit (FCU) 412, a USB (Universal Serial Bus (USB)413, an Institute of Electrical and Electronics Engineers 1394(IEEE1394) interface 414 are connected to the ASIC 406 through the PCIbus.

The operation panel 411 is directly connected to the ASIC 406. The MEM-C407 is a local memory used as a copying image buffer and a code buffer.The HDD 408 is a storage to accumulate image data, a program, font data,and a form.

Further, the HDD 408 stores a license file of an application executed bythe multifunction peripheral 10. The AGP bus 405 is a bus interface fora graphic accelerator card proposed to make a graphic process at a highrate. When the AGP bus directly accesses the MEM-P 402 at a highthroughput, the graphic accelerator card can be processed at a highrate.

Function of the Information Processing System

FIG. 7A is an example of a functional block diagram for explaining thefunction of the information processing system 100. Hereinafter, thefunctions of the cloud server 50 and the multifunction peripheral 10 aredescribed.

[[Multifunction Peripheral 10]]

The multifunction peripheral 10 includes a communication unit 11, anoperation receiving unit 12, a login requesting unit 13, and a displayprocessing unit 14. These various functions are implemented by the CPU401 when the program 408 p deployed from the HDD 408 to the MEM-P 402illustrated in FIG. 6. This program 408 p may be delivered from a serverfor delivering a program or may be stored in a portable recording mediumsuch as a universal serial bus (USB) memory and an optical recordingmedium and distributed.

The communication unit 11 is substantialized when the CPU 401illustrated in FIG. 6 executes a program 408 p and controls the networkI/F 409 so that the communication unit 11 sends and receives variousinformation to and from the cloud server 50.

The operation receiving unit 12 is substantialized when the CPU 401illustrated in FIG. 6 executes the program 408 p and controls theoperation panel 411 so that the operation receiving unit 12 receivesvarious operations by the user for the multifunction peripheral 10.Within the embodiment, an input of user information mainly necessary fora login is received. User information is to specify the user and is, forexample, a user ID. The ID is an abbreviation of “identification” andmeans an identifier or identification information. The ID is one of aname, a sign, a character string, and a number, which are used touniquely distinguish a specific object and a combination of at least twoof the name, the sign, the character string, and the number. The IDdescribed below is similarly determined. At a time of authentication,the operation receiving unit 12 receives an input of the user ID and apassword. An IC card carried by the user may be read by an IC cardreader and writer.

The display processing unit 14 is substantialized by the CPU 401illustrated in FIG. 6 when the CPU 401 executes the program 408 p tocontrol the operation panel 411. The display processing unit 14 displaysa screen including various information on the operation panel 411.Within the embodiment, an app view of applications (apps) is displayedbased on a profile 9 sent from the cloud server 50.

[[Cloud Server 50]]

The cloud server 50 includes a communication unit 51, a profiledetermining unit 52, an authenticating unit 53, a tenant administeringunit 54, and a profile administering unit 55. These various functionsare implemented by the CPU 201 when the program 209 p deployed from theHDD 209 to the memory 202 illustrated in FIG. 5 is executed in the CPU201. This program 209 p may be delivered from a server for deliveringthe program or may be stored in the portable recording medium such asthe universal serial bus (USB) memory and an optical recording mediumand distributed.

The communication unit 51 is substantialized when the CPU 201illustrated in FIG. 5 executes a program 209 p and controls the networkdriver 205 so that the communication unit 51 sends and receives variousinformation to and from the multifunction peripheral 10.

The profile determining unit 52 is substantialized when the CPU 201illustrated in FIG. 5 executes a program 209 p to check a predeterminedcondition and determine the profile 9 to be sent to the multifunctionperipheral 10.

The authenticating unit 53 is substantialized when the CPU 201illustrated in FIG. 5 executes the program 209 p to authenticate theuser.

The tenant administering unit 54 is substantialized when the CPU 201illustrated in FIG. 5 executes the program 209 p or by the memory 202 toadminister the tenant, the user, and the multifunction peripheral 10.Specifically, the tenant administering unit 54 includes a tenantinformation 61, user registration information 62, and MFP registrationinformation 63, and sends information acquired from the tenantadministering unit 54 out to the profile determining unit 52.

The profile administering unit 55 is substantialized when the CPU 201illustrated in FIG. 5 executes the program 209 p or by the memory 202 toadminister the profile 9. Specifically, the profile 9 is administeredfor each multifunction peripheral 10 or each user.

TABLE 1 ITEM NAME SETUP VALUE EXAMPLE TENANT ID 111 TENANT NAME XYZTENANT OPEN RANGE 222 333 TENANT CONNECTION 222 RANGE 333 444 555

Table 1 represents an example of the tenant information 61. The tenantinformation 61 includes items of a tenant ID, a tenant name, a tenantopen range, a tenant connection range. The tenant ID is information (anexample of group identification information) for specifying the tenant.The tenant name is a name or a nominal designation, by which the userdistinguishes the tenant.

The tenant open range corresponds to a tenant identifier of anothertenant which can access the tenant of oneself. The word “access” means atransmission and an acquisition of information by means ofcommunications. An example of the information transmitted in the accessis the profile 9 of the embodiment. Therefore, the tenant open rangecorresponds to tenant ID of another tenant which can provide the profileto the tenant of oneself. For example, the tenant having the tenant IDof “222” can provide the profile 9 to the tenant of oneself having thetenant ID of “111”. The tenant open range is an example of first requestpermission information.

Meanwhile, the tenant connection range corresponds to the tenant ID (thetenant ID of the another tenant, to which the tenant of oneself canprovide the profile) of the another tenant, to which the tenant ofoneself can access. The tenant connection range is an example of secondrequest permission information. For example, the tenant of oneselfhaving the tenant ID of “111” can provide the profile 9 to the tenanthaving the tenant ID of “222”. In a case where the user registered inthe tenant 111 uses the multifunction peripheral 10 registered in thetenant 222, it is sufficient that the tenant open range exists. However,there is a probability that an app of acquiring external information isset depending on the profile having the tenant ID of 111, for example.Therefore, an administrator or the like may wish to previously limit theoperation of the multifunction peripheral 10 based on the profile. Then,because the tenant, to which the tenant of oneself can provide theprofile, is set to be in the tenant connection range, it is possible toprevent the multifunction peripheral 10 in the another tenant fromoperating beyond the scope of the assumption using the profile providedby the tenant of oneself.

Therefore, there may be a case where a contradiction exists between atenant open range and a tenant connection range. For example, even ifthe tenant ID of 222 is set to the tenant open range, the tenant ID of111 may not be registered in the tenant connection range of the tenant.Within the embodiment, this point is considered to determine the profile9 to be provided to the multifunction peripheral 10.

Both of the tenant open range and the tenant connection range are awhite list. However, the tenant open range and the tenant connectionrange may be expressed by a black list, in which a tenant ID to bebanned to open or connect is registered. Further, the tenant open rangeand the tenant connection range may have multiple setup values. Thetenant open range and the tenant connection range may have no setupvalue.

TABLE 2 TENANT ID USER ID 111 user101 111 user102 111 user103 222user201 222 user202 333 user301 333 user302 444 user401

The user registration information 62 is schematically illustrated inTable 2. The tenant ID and the user ID are associated in the userregistration information 62. With this, the cloud server 50 can specifythe tenant in which the user is registered. The operation receiving unit12 of the multifunction peripheral 12 receives this operation.

TABLE 3 APPARATUS TENANT ID INFORMATION 111 machine101 111 machine102222 machine201 333 machine301 333 machine302 333 machine303

The multifunction peripheral (MFP) registration information 63 isschematically illustrated in Table 3. The tenant ID and apparatusinformation are associated in the MFP registration information 63. Theapparatus information is information of specifying the multifunctionperipheral 10. The apparatus information may be referred to as anapparatus ID or apparatus identification information. With this, thecloud server 50 can specify the tenant, in which the multifunctionperipheral 10 is registered. The MFP registration information 63 is anexample of an apparatus information memory unit.

FIG. 7B illustrates an example of a data structure of the profile 9.Each one profile 9 includes profile information 301, at least one appinformation 302, at least one app setup 303, layout information 304, anduser interface (UI) customize information 305. Profile information 301is bibliographic information of the profile 9 and includes a profile ID,a profile name, and an administration source tenant ID. The profile IDis information for specifying the profile 9. The profile name is a nameor a nominal designation of the profile 9. The administration sourcetenant ID designates a tenant administering the tenant. There is a casewhere multiple profiles are registered in one tenant. This is becausethe administrator creates several profiles so that one of the profilesis caused to be used by the multifunction peripheral 10 or the user.Alternatively, this is because the profile 9 is created for each user.Accordingly, in a case where there are multiple profiles 9 of the sameadministration source tenant ID, a default profile 9 is previouslydetermined. Instead, the user ID or the like is associated the profile9. In the default profile 9, a predetermined mark such as (*) isattached to the profile ID. Alternatively, the profile 9 having thenewest profile ID is determined as the default.

The app information 302 is information of the app included in theprofile 9. The “app Z1” of the app information 302 identifies as theapp. The “app screen 521 part” is a part of a user interface which theapp display on the multifunction peripheral 10.

The app setup 303 is information relater to a setup of the app. Each appsetup 303 is associated with each app information 302. In a case wherethe app is a scan app, a scan setup (mononchrome/color, resolution,density, or the like) is registered. In a case where the app is a printapp, a print setup (paper size, mononchrome/color, double side,aggregation, finishing, or the like) is registered. The app setup 303includes an individual setup for each user.

The layout information 304 has a basic layout structure of the userinterface. The “2×3” means that icons of the app are arranged in 2rows×3 columns. A placement order of the UI customize information 305 isa piaais a placement order of the app in a user interface set by theuser.

Operation Procedure

FIG. 8 is an example of a sequence diagram illustrating a login to thecloud server 50 using the multifunction peripheral 10 of the tenant, inwhich oneself is not registered, and the profile 9 of oneself is used inthe multifunction peripheral 10. Referring to FIG. 9, an example of ascreen is described. FIG. 9 illustrates a transition example of thescreen displayed on the operation panel.

The user conducts an operation of displaying the app home screen on themultifunction peripheral 10 (step S1). The user conducts an operation ofdisplaying the app home screen 501 on the multifunction peripheral 10.

When the operation receiving unit 12 receives this operation, theoperation receiving unit 12 requests the communication unit 11 toacquire the profile 9 (step S2).

The communication unit 11 of the multifunction peripheral 10 sends theacquisition request to acquire the profile 9 to the cloud server 50(step S3). The acquisition request includes the apparatus information ofthe multifunction peripheral 10.

When the communication unit 51 of the cloud server 50 receives theacquisition request to acquire the profile 9, the communication unit 51sends out the acquisition request to acquire the profile 9 to theprofile determining unit 52 while designating the apparatus information(step S4).

The profile determining unit 52 requests the tenant administering unit54 to send the tenant information 61 of the tenant, in which themultifunction peripheral 10 is registered in step S5.

The tenant administering unit 54 acquires the tenant ID associated withthe apparatus information with reference to the MFP registrationinformation 63 (step S6). Next, the tenant administering unit 54acquires the tenant information 61, in which this tenant ID isregistered, and sends out the acquired tenant information 61 to theprofile determining unit 52.

Next, the profile determining unit 52 requests the profile administeringunit 55 to send the profile ID of the profile 9 corresponding to thetenant ID by designating the tenant ID of the tenant information 61acquired in step S6.

The profile administering unit 55 specifies the profile 9 using thedesignated tenant ID as the administration source tenant ID and acquiresthe profile ID from this profile 9 (step S8). The profile administeringunit 55 sends the profile ID to the profile determining unit 52. In acase where the number of the profiles 9 having the same administrationsource tenant ID is multiple, all the profile IDs are sent.

The profile determining unit 52 requests the profile administering unit55 to send the profile 9 by designating the profile ID (step S9). In acase where multiple profile IDs are sent out of the profileadministering unit 55, the profile determining unit 52 specifies adefault profile ID and thereafter requests the profile administeringunit 55 to send the profile 9 while designating the profile ID.

The profile administering unit 55 sends the profile 9 specified by theprofile ID to the profile determining unit 52 (step S10).

The profile determining unit 52 sends the acquired profile 9 to thecommunication unit 51 (step S11).

The communication unit 51 of the cloud server 50 receives the profile 9and sends the profile 9 to the multifunction peripheral 10 (step S12).

The communication unit 11 of the multifunction peripheral 10 receivesthe profile 9 and sends the profile 9 to the display processing unit 14(step S13).

The display processing unit 14 displays an app home screen based on theprofile 9 on the operation panel (step S14). Referring to FIG. 9, (a)illustrates an example of the app home screen. This app home screen isbased on the profile 9 of the multifunction peripheral 10. The displayprocessing unit 14 caches the profile 9 to use the profile 9. With this,the image forming apparatus may not acquire the profile 9 from the cloudserver 50 at every screen transition. The “caching” is to store data ina memory device such as an HDD 209.

Next, the user logs into the cloud server 50 to set the profile 9ordinarily used by the user to the multifunction peripheral 10.

The user conducts operations of inputting the user ID and the passwordto log in using a login screen (step S21). FIG. 9(b) illustrates anexample of the login screen. The user inputs the user ID and thepassword in the login screen.

The operation receiving unit 12 of the multifunction peripheral 10receives this operation and sends a login request including the user IDand the password to the login requesting unit 13 (step S22).

The login requesting unit 13 sends the login request including the userID, the password, and the apparatus information to the communicationunit 11 (step S23).

The communication unit 11 sends a login request including the user ID,the password, and the apparatus information to the cloud server 50 (stepS24).

The communication unit 51 of the cloud server 50 receives the loginrequest and sends the login request and the apparatus information to theprofile determining unit 52 (step S25).

The profile determining unit 52 designates the apparatus information andrequests the tenant administering unit 54 to send the tenant information61 of the tenant, in which the user is registered, in step S26. Theapparatus information is sent from another multifunction peripheral 10to the cloud server 50. Therefore, at the time of the login, the tenantinformation 61 is specified based on the apparatus information anew.

The tenant administering unit 54 acquires the tenant ID associated withthe apparatus information with reference to the MFP registrationinformation 63 (step S27). Next, the tenant administering unit 54acquires the tenant information 61, in which this tenant ID isregistered, and sends out the acquired tenant information 61 to theprofile determining unit 52.

Next, the profile determining unit 52 requests the authenticating unit53 to authenticate not only user ID and the password but also the user(step S28).

The authenticating unit 53 uses the user ID and the password toauthenticate the user (step S29). Specifically, it is determined whethera set of the user ID and the password is registered in theauthenticating unit 53. If the set of the user ID and the password isregistered in the authenticating unit 53, it is determined that theauthentication is successful (OK). If the set of the user ID and thepassword is not registered in the authenticating unit 53, it isdetermined that the authentication is unsuccessful (NG).

If it is determined that the authentication is successful, the profiledetermining unit 52 designates the user ID and acquires the tenantinformation of the tenant information 61, in which the user isregistered, from the tenant administering unit 54 (step S30).

The tenant administering unit 54 acquires the tenant ID from the userregistration information 62, and thereafter sends out the tenantinformation 61 of the tenant ID to the profile determining unit (stepS31).

The profile determining unit 52 determines the profile 9 sent to themultifunction peripheral 10 in response to whether the tenant, in whichthe multifunction peripheral 10 is registered, and the tenant, in whichthe user is registered, are the same (step S32). Referring to FIG. 10, aprocedure of this determination is explained.

The profile determining unit 52 requests the profile administering unit55 to send the profile 9 by designating the profile ID (step S33).

The profile administering unit 55 sends the profile 9 specified by theprofile ID to the profile determining unit 52 (step S34).

The profile determining unit 52 sends the acquired profile 9 and a loginresult to the communication unit 51 (step S35).

The communication unit 51 of the cloud server 50 sends the profile 9 andthe login result to the acquisition request to acquire the profile 9 tothe multifunction peripheral 10 (step S36).

The communication unit 11 of the multifunction peripheral 10 receivesthe profile 9 and the login result, and sends out the profile 9 and thelogin result to the login requesting unit 13 (step S37).

The login requesting unit 13 sends the profile 9 and the login resultout to the display processing unit 14 (step S38).

The display processing unit 14 displays the app home screen based on theprofile 9 on the operation panel (step S39). Referring to FIG. 9, (c)and (d) illustrate app home screens after the login. There are two typesof the app home screen displayed after the login, namely (c) and (d) inFIG. 9. Two types of the app home screen will be described in detaillater.

[[Transition of Screen]]

The screens in FIG. 9 are described. Referring to FIG. 9, (a) is the apphome screen 501, on which an icon 503 for launching an app operable inthe multifunction peripheral 10 and a login button 502. When a loginbutton 502 is pushed, a login screen 511 in (b) of FIG. 9 is displayed.Although the user can launch the app without the login, an app setup forthe user is not reflected.

The login screen 511 in (b) of FIG. 9 includes the user ID, an inputcolumn 512 for the password, and a login request button 513. The loginrequest button 513 is provided to cause the multifunction peripheral 10to send the user ID and the password. As an example of the user ID, amail address is input in (b) of FIG. 9. The user ID may be informationof specifying the user.

In a case where the login is OK, the app home screen 501 in (c) or (d)of FIG. 9 is displayed. Referring to FIG. 9, (c) illustrates the apphome screen 501 in a case where the tenant, in which the user isregistered, and the tenant, in which the multifunction peripheral 10 isregistered, are the same from among the app home screens after thelogin. In a case where the tenant is the same, the profile 9 is also thesame. Therefore, the outer appearance of the app home screen 501 doesnot different from the outer appearance before the login illustrated in(a).

Referring to FIG. 9, (d) illustrates the app home screen 501 in a casewhere the tenant, in which the user is registered, and the tenant, inwhich the multifunction peripheral 10 is registered, are different fromamong the app home screens after the login. Because the app home screen501 is displayed based on the profile 9 of the user, the outerappearance of the app home screen 501 changes from that illustrated in(a) of FIG. 9.

In a case where the login is NG, the app home screen 501 being the sameas that illustrated in (a) of FIG. 9 is displayed.

[[Determination of the Profile ID]]

FIG. 10 is an example of a flowchart for explaining a procedure ofdetermining a profile ID based on tenant information 61 of themultifunction peripheral 10 and tenant information 61 of the user.

At first, the profile determining unit 52 determines whether the tenantID of the multifunction peripheral 10 matches the tenant ID of the user(step S110).

When the tenant ID of the multifunction peripheral 10 matches the tenantID of the user (YES in step S110), any one of the tenant IDs can besimilarly used to determine the profile ID. Therefore, the profile ID isdetermined so that the tenant ID of the user is the administrationsource tenant ID (step S120).

When the tenant ID of the multifunction peripheral 10 does not match thetenant ID of the user (NO in step S110), a tenant open range of thetenant information 61 of the multifunction peripheral 10 is referred to(step S130).

Then, the profile determining unit 52 determines whether the tenant IDof the tenant of the user is included in the tenant open range of thetenant of the multifunction peripheral 10 (step S140). Said differently,it is determined whether the tenant of the multifunction peripheral 10permits that the profile is acquired from the tenant of the user.

When the determination in step S140 is NO, the profile 9 of the usercannot be referred to. Therefore, the profile determining unit 52determines the profile ID, in which the tenant ID of the multifunctionperipheral 10 is the administration source tenant ID (step S150).

When the determination in step S140 is YES, the tenant connection rangeof the tenant of the user is referred to (step S160).

Then, the profile determining unit 52 determines whether the tenant IDof the tenant of the multifunction peripheral 10 is included in thetenant connection range of the tenant (step S170). Said differently, itis determined whether the tenant of the user permits to provide theprofile to the tenant of the multifunction peripheral 10.

When the determination in step S70 is NO, the profile 9 of the usercannot be acquired. Therefore, the profile determining unit 52determines the profile ID, in which the tenant ID of the multifunctionperipheral 10 is the administration source tenant ID (step S150).

When the determination in step S170 is YES, the tenant of themultifunction peripheral 10 can acquire the profile 9 of the user fromthe tenant of the user, and the tenant of the user permits the tenant ofthe multifunction peripheral 10 to provide with the profile 9 of theuser. Therefore, the profile determining unit 52 determines the profileID, in which the tenant ID of the user is the administration sourcetenant ID (step S120).

Next, the profile determining unit 52 determines that the profile 9 ofthe determined profile 9 as the profile 9 to be sent to themultifunction peripheral 10 (step S180).

In the process illustrated in FIG. 10, the cloud server can control sothat the profile 9 administered by the tenant, in which the user isregistered, is always sent to the multifunction peripheral 10. In thiscase, when the tenant ID of the multifunction peripheral 10 does notmatch the tenant ID of the user (NO in step S110), the profiledetermining unit 52 determines whether there is a setup of giving apriority to the profile 9 administered by a tenant, in which the user isregistered. When there is the setup of giving the priority to theprofile 9, the process of step S120 is conducted. With this, even in acase where the tenant ID of the multifunction peripheral 10 does notmatch the tenant ID of the user, the profile 9 administered by thetenant, in which the user is registered, is always sent to themultifunction peripheral 10. In this case, the user is always enabled touse the same profile 9 without any limitation. For example, in themultifunction peripheral 10 installed in a public area such as aconvenience store, the user can always use the same app home screen.

Case where Authentication of User is NG

In a case where authentication of the user is NG (unsuccessful), thecloud server 50 may not provide the profile 9 administered by thetenant, in which the user is registered. Therefore, the profile 9administered by the tenant, in which the multifunction peripheral 10 isregistered as follows, is provided.

FIG. 11 is an example of a sequence diagram illustrating a login to thecloud server 50 using the multifunction peripheral 10 of the tenant, inwhich oneself is not registered, and the profile 9 of oneself is used inthe multifunction peripheral 10. Referring to FIG. 11, a difference fromFIG. 8 is mainly described.

The processes of steps S1 to S14 and steps S21 to S28 are similar toFIG. 8.

The authenticating unit 53 uses the user ID and the password toauthenticate the user (step S291). Here, because a set of the user IDand the password is not registered in the authenticating unit 53, theauthentication is unsuccessful (NG).

Because the authentication is unsuccessful (NG), the profile determiningunit 52 sends out the login result (NG) to the communication unit 51(step S301).

The communication unit 51 of the cloud server 50 sends the login result(NG) to the multifunction peripheral 10 (step S311).

The communication unit 11 of the multifunction peripheral 10 receivesthe login result (NG) and sends out the login result (NG) to the loginrequesting unit 13 (step S321).

The login requesting unit 13 sends out the login result (NG) to thedisplay processing unit 14 (step S331).

The display processing unit 14 displays the app home screen based on theprofile 9 cached in step S14 on the operation panel because the loginresult is NG (step S341). Therefore, the app home screen illustrated in(c) of FIG. 9 is displayed. As described, in a case where the login isnot possible, the user can use the multifunction peripheral 10.

As described, the information processing system 100 can set the profile9 administered by the tenant, in which the user is registered, to themultifunction peripheral 10 in a case where the tenant, in which themultifunction peripheral 10 is registered, differs from the tenant, inwhich the user is registered. The user can use the multifunctionperipheral 10 in an environment the same as an ordinary environment.

Second Embodiment

The process of the first embodiment enables the user to use the profile9 ordinarily used by the user in the multifunction peripheral 10registered in the tenant, in which the user is not registered.

However, when the user uses the app by logging in the cloud server 50from the multifunction peripheral 10 of the tenant, in which the user isnot registered, an inconvenience related to billing or the like occurs.Said differently, in a case where the user prints using themultifunction peripheral 10 of another tenant in pull printing, forexample, a cost related to printing is billed to the tenant, in whichthe user is not registered. Depending on the app, there is a case wherethe multifunction peripheral 10 accesses an external server. However,there may exist a tenant, which does not wish to permit an access to theexternal server in consideration of security.

Further, for the tenant of oneself, in which the user is registered, itis wished to limit that the user of the tenant of oneself arbitrarilyuse the multifunction peripheral 10 that is registered in anothertenant.

Within the second embodiment, described is the information processingsystem 100 of limiting a usable function in a case where the user ofanother tenant uses the multifunction peripheral 10 of the tenant ofoneself and a case where the user of the tenant of oneself uses themultifunction peripheral 10 of another tenant.

The user of the tenant of oneself represents a certain user registeredin a certain tenant, and the user of another tenant represents a userwho is not registered in the tenant of oneself.

In the information processing system 100 of the second embodiment, ausable function of the multifunction peripheral 10 of the tenant ofoneself usable by the user of another tenant is registered in the tenantinformation 61. Further, a function of another tenant usable by the userof the tenant of oneself is registered in the tenant information 61.With this, it is possible to display only an app permitted to use in thetenant information 61 from among the apps designated by the profile 9.Thus, it is possible to limit the function usable by the user.

Function

FIG. 12 is logs into an example of a functional block diagram forexplaining the function of the information processing system 100.Referring to FIG. 12, the structural elements having the same referencesymbols as FIG. 7A perform similar functions. Therefore, only majorstructural elements of the second embodiment may be described.

[[Cloud Server 50]]

Within the second embodiment, the cloud server 50 includes an appdetermining unit 56 and an app administering unit 57 in addition to FIG.7A. The app determining unit 56 is substantialized when the CPU 201illustrated in FIG. 5 executes a program 209 p and determines an app tobe displayed on the multifunction peripheral 10.

The app administering unit 57 is substantialized when the CPU 201illustrated in FIG. 5 executes the program 209 p or by the memory 202 toadminister the app. Specifically, there is app information, in whichfunctions of the multifunction peripheral 10 used by the apps areregistered by each of the apps.

Further, within the second embodiment, the tenant information 61administered by the tenant administering unit 54 is different from thefirst embodiment.

TABLE 4 ITEM NAME SETUP VALUE EXAMPLE TENANT ID 111 TENANT NAME TENANT 1TENANT OPEN RANGE 222 333 AVAILABLE FUNCTION OF PRINT, SCAN TENANT OPENRANGE TENANT CONNECTION 222 RANGE 333 444 555 AVAILABLE FUNCTION OFSCAN, OCR, TENANT CONNECTION EXTERNAL SERVICE RANGE CONNECTION

Table 4 represents an example of the tenant information 61. Incomparison with Table 1, the tenant information 61 of Table 4 includesan available function of tenant open range and an available function oftenant connection range. The available function of tenant open range isa function which can be used at a time when the user of another tenantlogs into the multifunction peripheral 10 of the tenant of oneself (anexample of first permission function information). When the user of atenant A logs into the multifunction peripheral 10 of a tenant B, theavailable function of tenant open range is specified by the tenant IDassociated with the multifunction peripheral 10 of the tenant B. Thus, afunction usable by the user of the tenant A is limited.

The available function of tenant connection range is a function whichcan be used at a time when the user of the tenant of oneself logs intothe multifunction peripheral 10 of another tenant (an example of secondpermission function information). When the user of the tenant A logsinto the multifunction peripheral 10 of the tenant B, the availablefunction of tenant connection range is specified by the tenant IDassociated with the user ID. Thus, a function usable by the user of thetenant A is limited.

The available function of tenant open range and the available functionof tenant connection range may have multiple setup values. The availablefunction of tenant open range and the available function of tenantconnection range may not have a setup value at all.

Although both the available function of tenant open range and theavailable function of tenant connection range are white lists, both theavailable function of tenant open range and the available function oftenant connection range may be a black list, in which a function of anopen or a connection is prohibited.

The external service connection of the available function of tenantconnection range is a function of uploading image data (step Scan data)obtained by scanning to the external storage, and/or a function ofacquiring (and subsequently printing) data from the external storageservice. The service name of the external storage service is, forexample, google drive (“google drive” is a registered trademark) anddrop box (“google drive” is a registered trademark).

TABLE 5 ITEM NAME SETUP VALUE EXAMPLE APP ID 123 APP NAME COPY APP USEFUNCTION COPY SCAN

TABLE 6 ITEM NAME SETUP VALUE EXAMPLE APP ID 456 APP NAME Scan to folderUSE FUNCTION SCAN EXTERNAL SERVICE CONNECTION

Tables 5 and 6 represent examples of app information. Table 5 representsthe app information of the copy app as an example. Table 6 representsthe app information of Scan to folder as an example. The “Scan tofolder” is the app, by which image data of an original manuscript readusing the function of scanning by the multifunction peripheral 10 issent to and stored in a predetermined folder.

The app information includes items and setup values of an app ID, an appname, and a use function. The app ID is information for specifying theapp. The app name is the name or the nominal designation of the app. Theuse function is a function used by the app. For example, the app calledCopy uses functions of copy and scan. The app called Scan to folder usesfunctions of scan and external service connection. When the user usesthe app, a use of the use function may be permitted. Therefore, in acase where the use function is included in an available function oftenant open range or an available function of tenant connection range,the user can use the app.

A setup value of the use function may be plural. Therefore, in a casewhere the user uses the app, all the use functions may be included inthe available function of the tenant open range or the availablefunction of the tenant connection range.

Operation Procedure

FIG. 13 is an example of a sequence diagram illustrating a login to thecloud server 50 using the multifunction peripheral 10 of the tenant, inwhich oneself is not registered, and the profile 9 of oneself is used inthe multifunction peripheral 10. Referring to FIG. 13, a difference fromFIG. 8 is mainly described.

Processes of steps S1 to S14 and steps S21 to S34 may be similar to thesteps in FIG. 8. The profile determining unit 52 acquired the profile 9reflects a use function limitation to the profile 9 (step S342). Theprofile determining unit 52 sends out the profile 9, the tenantinformation 61 of the multifunction peripheral 10, and the tenantinformation 61 of the user. The process in the app determining unit 56is described later with reference to FIG. 14.

The app determining unit 56 sends out the profile 9 including only theavailable app after reflecting the use limitation to the profiledetermining unit 52 (step S343). Subsequent processes of steps S35 toS39 may be similar to those in FIG. 8.

[[Reflection of Use Limitation]]

FIG. 14 is an example of a flowchart illustrating a procedure that theapp determining unit 56 limits an app usable by the user. By the processillustrated in FIG. 14, an app which does not operate using theavailable function is omitted from among the apps registered in theprofile 9 determined in step S34 of FIG. 13. FIG. 15 explains the uselimitation using specific apps.

The app determining unit 56 refers to the tenant information 61 of themultifunction peripheral 10 and the tenant information 61 of the userand determines whether the tenant ID of the multifunction peripheral 10matches the tenant ID of the user (step S210).

In the case where the tenant ID of the multifunction peripheral 10matches the tenant ID of the user (YES in Step S210), the available appis not limited. Therefore, the app determining unit 56 does not omit theapp registered in the profile 9.

In the case where the tenant ID of the multifunction peripheral 10 doesnot match the tenant ID of the user (NO in Step S210), an app using afunction not registered (a function other than the registered function)in the available function of the tenant open range of the tenantinformation 61 is omitted from the apps registered in the profile 9(step S220). Specifically, the app determining unit 56 reads out theavailable function of the tenant open range from the tenant information61 of the multifunction peripheral 10. Next, all the app registered inthe profile 9 are read out. The app determining unit 56 acquires the usefunction used by each app from the app information administered by theapp administering unit 57. Then, the use function used by the appregistered in the profile 9 is specified. It is determined whether theuse function is registered in the available function of the tenant openrange. Because the app which is not registered is not available, such anapp is omitted from the profile 9 by the app determining unit 56.

Next, the app determining unit 56 conducts a process similar to theabove for the available function of the tenant connection range. Saiddifferently, the app determining unit 56 omits the app using thefunction not registered (the function other than the registeredfunction) in the available function of the tenant connection range ofthe tenant information 61 from the apps registered in the profile 9(step S230). Specifically, the app determining unit 56 reads out theavailable function of the tenant connection range from the tenantinformation 61 of the user. Next, all the apps not omitted in step S220are read out. The app determining unit 56 acquires the use function usedby each app from the app information 56 administered by the appadministering unit 57. Then, the use function used by the app notomitted in step S220 is specified. It is determined whether the usefunction is registered in the available function of the tenantconnection range. Because the app which is not registered is notavailable, such an app is omitted from the profile 9 by the appdetermining unit 56.

Whichever a step S220 or a step S230 may be determined earlier.

Even in a case where the tenant of the multifunction peripheral 10 isdetermined to match the tenant of the user in step S210, the appdetermining unit may limit the use any way. For example, an app otherthan the app having the function permitted by the tenant of themultifunction peripheral 10 is omitted from the profile. With this, in acase where the user of the tenant of oneself uses the multifunctionperipheral 10 of the tenant of oneself, the use can be limited. Forexample, the function which is not temporarily used by the tenant ofoneself may be subjected to the use limitation.

[[Screen Example]]

FIG. 15 is an example of explaining a flow of an excluding process ofthe app using the use limitation. Referring to FIG. 15, (a) illustratesa view of apps registered in the profile. Said differently, (a)illustrates at least one app (print, scan, scan OCR, print scan, andscan external service) in an initial stage before omitting the app.

The available function of the tenant open range of the tenantinformation 61 of the multifunction peripheral 10 is print, scan, andOCR. Among these, because there is not a function (an external serviceconnection) required by an app called the scan external service, the appdetermining unit 56 omits the app called the scan external service.Referring to FIG. 15, (b) illustrates the app view from which the scanexternal service is omitted from the profile 9.

Here, the available function of the tenant connection range of thetenant information 61 of the user is print and scan. Because there isnot a function (OCR between scan and OCR) necessary for a scan OCR, theapp determining unit 56 omits the app of scan OCR. Referring to FIG. 15,(c) illustrates the app view from which the scan external service andthe scan OCR are omitted from the profile 9. As such, it is possible tolimit the use of the app, which the user can not use in another tenant.

Within the above process, it is possible to limit a usable function in acase where the user of another tenant uses the multifunction peripheral10 of the tenant of oneself and a case where the user of the tenant ofoneself uses the multifunction peripheral 10 of another tenant. If onlythe process of step S220 illustrated in FIG. 14 is performed, it ispossible to limit the usable function in a case where the user of theother tenant uses the multifunction peripheral 10 of the tenant ofoneself. If only the process of step S230 illustrated in FIG. 14 isperformed, it is possible to limit the usable function in a case wherethe user of the tenant of oneself uses the multifunction peripheral 10of another tenant.

Use Limitation for Each Detailed Function as an Element of the Function

Within the second embodiment, the use of the app is limited for eachfunction (in a unit of the function). Further, it is possible to limitthe use of the app for each detailed function. Said differently, theentire function of the print is not limited but, for example, only acolor print can be limited in the print. The detailed function is thefunction to be the element of realizing the function. Described below isa detailed function.

TABLE 7 BASIC FUNCTION DETAILED FUNCTION PRINT BLACK AND WHITE COLORDUPLEX SIMPLEX A4 SCAN RESOLUTION COLOR BLACK AND WHITE PDF OCR ENGLISHJAPANESE EXTERNAL SERVICE Google (REGISTERED TRADEMARK) CONNECTIONoffice365 (REGISTERED TRADEMARK)

Table 7 represents an example of detailed functions of each function.For example, the function of the print includes the detailed function sof black and white, color, duplex, simplex, and A4. In a manner similarthereto, each function of scan, OCR, and an external service connectionhas the detailed functions. These detailed functions can be set to theavailable function of the tenant open range or the available function ofthe tenant connection range. In this case, the detailed function is setto the app information for each app.

TABLE 8 ITEM NAME SETUP VALUE EXAMPLE TENANT ID 111 TENANT NAME TENANT 1TENANT OPEN RANGE 222 333 DETAILED FUNCTION FUNCTION AVAILABLE FUNCTIONOF PRINT BLACK AND TENANT OPEN RANGE WHITE TENANT CONNECTION 222 RANGE333 444 555 DETAILED FUNCTION FUNCTION AVAILABLE FUNCTION OF EXTERNALgoogle TENANT CONNECTION SERVICE RANGE CONNECTION

Table 8 represents an example of the tenant information 61, to which thedetailed function is set. The detailed function of the black and whiteis registered to the function of the print in the available function ofthe tenant open range. Then, in a case where the user of another tenantlogs into the multifunction peripheral 10 of the tenant of oneself, onlythe detailed function of the black and white in the print can be used.The app determining unit 56 deletes the app requiring the function otherthan the detailed function from the profile. The multifunctionperipheral 10 displays the app using the print. However, only the “blackand white” is displayed as an option of the print color. In this case,the app determining unit 56 does not exclude the app of the print butexcludes the option other than the black and white inside the app.

Further, in the available function of the tenant connection rangerepresented by Table 8, the detailed function of google (“google” is theregistered trademark) is registered in the function of the externalservice connection. Then, in a case where the user of the tenant ofoneself logs into the multifunction peripheral 10 of another tenant,only the detailed function of google (“google” is the registeredtrademark) can be used as the external service connection. The appdetermining unit 56 does not omit the app of the scan external servicebut omits an option other than google (“google” is the registeredtrademark).

As such, the use limitation is conducted for each detailed function.Therefore, the entire app is not subjected to the use limitation but thedetailed use limitation is possible while permitting to use the app.

Third Embodiment

The process of the first embodiment enables the user to use the profile9 ordinarily used by the user in the multifunction peripheral 10registered in the tenant, in which the user is not registered. Withinthe second embodiment, the use of the app can be limited.

However, as explained in the first and second embodiments, the profile 9used by the user is determined by the cloud server 50 and is sent to themultifunction peripheral 10. Therefore, the performance may become low.Specifically, a long time elapses to send the profile 9, and there is arisk that a waiting time after the user logs into and before the apphome screen is displayed becomes long.

Within the third embodiment, in a case where the user of another tenantlogs into through the multifunction peripheral 10 of the tenant ofoneself, it is possible to prevent the performance of the informationprocessing system 100 from degrading by using the profile 9 cached bythe multifunction peripheral 10. This information processing system 100is described next.

Function

FIG. 16 is an example of a functional block diagram for explaining thefunction of the information processing system 100. Referring to FIG. 16,the structural elements having the same reference symbols as FIG. 7Aperform similar functions. Therefore, only major structural elements ofthe third embodiment may be described.

[[Multifunction Peripheral 10]]

The multifunction peripheral 10 includes a profile processing unit 15 incomparison with FIG. 7A. The profile processing unit 15 issubstantialized when the CPU 401 illustrated in FIG. 6 executes aprogram 408 p to administer the profile in the multifunction peripheral10. Specifically, the profile processing unit 15 performs caching,combining, restoring, and administering in a situation of multipleprofiles.

[[Cloud Server 50]]

In comparison with FIG. 7A, the cloud server 50 of the third embodimentincludes a profile difference determining unit 58. The profiledifference determining unit 58 is substantialized by the CPU 201(illustrated in FIG. 5) executing the program 209 p. The profiledifference determining unit 58 determines a difference between theprofile 9 administered by the tenant of the multifunction peripheral 10and the profile 9 administered by the tenant of the user and produces aprofile difference (difference information of setup information).

Operation Procedure

FIG. 17 is an example of a sequence diagram illustrating a login to thecloud server 50 using the multifunction peripheral 10 of the tenant, inwhich oneself is not registered, and the profile 9 of oneself is used inthe multifunction peripheral 10. Referring to FIG. 17, a difference fromFIG. 8 is mainly described. Here, for convenience of explanation, themultifunction peripheral 10 is registered in the tenant B and the useris registered in the tenant A. Further, the tenant B uses the profile 9(first setup information) having a profile ID of V1.3.B, and the tenantA uses the profile 9 (step Second setup information) having a profile IDof V1.1.A.

A process of steps S1 to S9 may be similar to those in FIG. 8. Theprofile administering unit 55 sends out the profile 9 having the profileID of V1.3.B, which is administered by the tenant B, to the profiledetermining unit 52 (step S10). Hereinafter, the profile ID isrepresented by (V1.3.B).

The profile determining unit 52 sends out the acquired profile 9(V1.3.B) to the communication unit 51 (step S11).

The communication unit 51 of the cloud server 50 sends the profile 9(V1.3.B) to the multifunction peripheral 10 (step S12).

The communication unit 11 of the multifunction peripheral 10 receivesthe profile 9 and sends the profile 9 (V1.3.B) to the display processingunit 14 (step S13).

The display processing unit 14 displays an app home screen based on theprofile 9 on the operation panel (step S14). The display processing unit14 caches this profile 9 (V1.3.B) in advance.

Subsequent processes of steps S21 to S22 may be similar to those in FIG.8. The login requesting unit 13 sends out a login request including auser ID, a password, the apparatus information, and a profile ID to thecommunication unit 11 (step S23).

The communication unit 11 sends a login request including the user ID,the password, the apparatus information, and the profile ID to the cloudserver 50 (step S24).

The communication unit 51 of the cloud server 50 receives the loginrequest and sends out the user ID, the password, the apparatusinformation, and the profile ID to the profile determining unit 52 (stepS25).

Subsequent processes of steps S26 to S32 may be similar to those in FIG.8. However, in step S27, the profile determining unit 52 acquires thetenant information 61 of the tenant B as the tenant information 61 ofthe multifunction peripheral 10. Further, in step S31, the profiledetermining unit 52 acquires the tenant information 61 of the tenant Aas the tenant information 61 of the user. In step S32, the profile IDadministered by the tenant A is determined to be V1.1.A.

The profile determining unit 52 sends out a profile ID (V1.3.B) cachedby the multifunction peripheral 10 and a profile ID (V1.1.A) determinedin step 32 together with the acquisition request to acquire the profileID to the profile administering unit 55 (step S33).

The profile administering unit 55 sends out the profile ID (V1.3.B)cached by the multifunction peripheral 10 and the profile ID (V1.1.A)determined in step 32 together with an acquisition request to acquire aprofile ID to the profile difference determining unit 58 (step S344).

The profile difference determining unit 58 generates a differenceprofile between two profiles 9 and sends out the difference profile tothe profile administering unit 55 (step S354). Referring to FIG. 18A toFIG. 18D, a method of producing the difference profile is explained.

The profile administering unit 55 sends out the difference profile tothe profile determining unit 52 (step S364).

Steps S374, S384, S394, and S404 become similar to steps S35 to S38illustrated in FIG. 8. The display processing unit 14 sends out thedifference profile and the cached profile 9 (V1.3.B) to the profileprocessing unit 15, and the profile processing unit 15 combines thedifference profile and the cached profile 9 (V1.3.B) to produce theprofile 9 (V1.1.A) administered by the tenant A (step S414). Thereafter,an app home screen is produced based on the produced profile 9 (V1.1.A).Further, the produced profile 9 (V1.1.A) is newly cached. In this case,if there is a space in a memory device, the produced profile 9 (V1.1.A)is cached together with the profile 9 (V1.3.B). If the space is not inthe memory device, the profile 9 (V1.1.A) is deleted and only theproduced profile 9 (V1.1.A) is cached (V1.3.B).

Because the difference profile is sent from the cloud server 50 to themultifunction peripheral 10 as described above, a communication time isshortened so as to improve the performance.

[[Difference Profile]]

FIG. 18A to FIG. 18D are an example illustrating the production of thedifference profile. FIG. 18A illustrates the profile 9 (V1.3.B)administered by the tenant B. FIG. 18B illustrates the profile 9(V1.1.A) administered by the tenant A. FIG. 18C illustrates the profile9 (V1.3.B) cached by the multifunction peripheral 10. FIG. 18Dillustrates the difference profile.

When the profile difference determining unit 58 compares the profile 9(V1.3.B) with the profile 9 (V1.1.A), it is known that app informationwhose app ID is “Z1” overlaps (is the same as) app information whose appID is “Y1”. The app information illustrated in FIGS. 18A to 18D hasfurther detailed information in comparison with the app informationillustrated in FIG. 7B. Said differently, the app information includesnot only an app part (an image) but also a resource such as an app icon,HTML/TEXT, and a program.

The profile difference determining unit 58 produces a differenceprofile, in which the app information 71 whose app ID is “Z1” and theapp information 71 whose app ID is “Y1” are not included. Although theapp information 71 whose app ID is “Z1” and the app information 71 whoseapp ID is “Y1” become unnecessary, a registration of the app information71 is recorded into the difference profile. Therefore, in the differenceprofile, the overlapping app information 71 becomes referenceinformation 60 indicative of profile Information of referencedestination. Here, the app information 71 of the apps Z1 and Y1 becomesthe reference information 60 referring to the apps Z1 and Y1 of “tenantB-V1.3.B”.

An app setup 303 may differ depending on the profile 9. Therefore, theapp setup 303 is not omitted in the difference profile. However, on thepremise that the user conducts the app setup, the app setup may beomitted.

When the profile 9 (V1.1.A) of the user is combined, the profileprocessing unit 15 replaces reference information 60 of the differenceprofile with app information 73 of the profile 9 (V1.3.B). Thus, theprofile 9 (V1.1.A) can be obtained by combining the difference profileand the profile 9 (V1.3.B).

FIG. 19 illustrates the combined profile 9 (V1.1.A). Thus, the referenceinformation 60 illustrated in FIG. 18D is replaced by the appinformation 73 illustrated in FIG. 18C. Therefore, it is known that thecombined profile 9 (V1.1.A) illustrated in FIG. 19 is the same as theprofile 9 (V1.1.A) administered by the tenant A illustrated in FIG. 18B.

As such, in the difference profile, the overlapping app information 71is replaced by the reference information 60. Therefore, thecommunication time between the cloud server 50 and the multifunctionperipheral 10 can be shortened. Although the communication time for theapp information is apt to be long because the app information has agreat size due to an inclusion of the image and the program, thedifference profile can omit sending of the app information so as toshorten a waiting time for the user. Accordingly, the performance can beimproved.

[[Profile 9 Cached after Logout]]

In a case where the multifunction peripheral 10 caches the combinedprofile 9 (V1.1.A) and also the profile 9 (V1.3.B), the multifunctionperipheral 10 deletes the profile 9 (V1.1.A) upon the logout of the userand caches the profile 9 (V1.3.B).

On the contrary, in a case where a capacity is saved at a time ofcaching two profiles 9, the process is as follows. FIG. 20 illustratesan example of explaining the profile after the logout. Firstly, when theprofile processing unit 15 combines the cached profile and thedifference profile, the profile processing unit 15 caches the profile 9(601 in FIG. 20, an example of a part information of claims) other thanthe app information 602 designated by the reference information 60.

The app information 602 referred by the reference information 60 iscombined with the difference profile as described above. At this time,the profile processing unit 15 takes out the reference information 60out of the difference profile and caches the reference information.Thus, without redundantly caching the app information designated by thereference information 60, the profile 9 (V1.3.B) can be restored.

After the user logs out, the app information 602 acquired from theprofile 9 (V1.3.B) from among the profile 9 (V1.1.A) can be known usingthe cached reference information 60. Therefore, the app information 602is taken out of the profile 9 (V1.1.A) and combined with the cachedprofile 9 (601). With this, the profile 9 (V1.3.B) cached in themultifunction peripheral 10 can be restored. Therefore, it is notnecessary that the multifunction peripheral 10 acquires the profile 9(V1.3.B) again from the cloud server 50.

FIG. 21A is an example of a flowchart illustrating a procedure that aprofile processing unit 15 processes the profile 9. FIG. 21B is anexample of another flowchart illustrating a procedure that the profileprocessing unit 15 restores the profile 9.

The profile processing unit 15 acquires the app information 602 of thetenant B designated by the reference information 60 of the differenceprofile from the profile 9 (V1.3.B) of the tenant B (step S310).

Next, the profile processing unit 15 caches the profile 9 (V1.3.B) ofthe tenant B, from which the app information 602 designated by thereference information 60 is deleted (step S320).

Next, the profile processing unit 15 acquires the reference information60 from the difference profile and caches the acquired referenceinformation 60 (step S330).

Next, the profile processing unit 15 combines the app information 602 ofthe profile 9 (V1.3.B) of the tenant B designated by the referenceinformation 60 with the difference profile (step S340). With this, theprofile 9 (V1.1.A) of the tenant A is combined.

After the user logs out, the profile processing unit 15 acquires the appinformation 602 designated by the reference information 60 from theprofile 9 (V1.1.A) of the combined tenant A (step S350).

Next, the profile processing unit 15 combines the profile 9 (V1.3.B) ofthe cached tenant B with the app information 602 (step S360).

Next, the profile processing unit 15 deletes the profile 9 (V1.1.A) ofthe combined tenant A (step S370). With this, the capacity of the memorydevice of the multifunction peripheral 10 can be reduced.

As described, because the profile 9 (V1.3.B) of the tenant B isrestored, it is possible to reduce a waiting time for the user of thetenant B of using the multifunction peripheral 10. Further, because theprofile 9 (V1.1.A) of the tenant A is deleted, the capacity of thememory device is hardly compressed.

[[Another Example of Caching Profile]]

After the user logs out, the profile processing unit 15 may cacheprofiles of multiple other tenants as long as the multifunctionperipheral 10 can hold the profile 9 (V1.1.A) without deleting theprofile 9 (V1.1.A) of the tenant A. In this case, after the number ofthe cached profiles reaches a predetermined number, the oldest profileis deleted. Then, the profile referred to by the multifunctionperipheral 10 increases to further improve the performance. In order toshorten the communication time for the profile, the profile processingunit 15 sends the profile ID of the profile. In a case where the profileID determined to be sent to the multifunction peripheral 10 is cached,it is sufficient that the profile ID is sent to the multifunctionperipheral 10. Therefore, the waiting time for the user can beshortened.

Using a structure similar thereto, the profile processing unit 15 mayadminister the profile based on the expiry date. In this case, theprofile having an elapsed expire date is earlier delete. Further, theprofiles of a predetermined number or more are deleted so that theprofile having the oldest data is earlier deleted.

The profile processing unit 15 can cache all the profiles, in which thedesignated tenant ID is the administration source tenant ID, within thetenant open range of the tenant information of the tenant, in which themultifunction peripheral 10 is registered. Because the profile, in whichthe tenant ID designated by the tenant open range is the administrationsource tenant ID, is highly probably used, the profile can beeffectively cached.

In this case, it is preferable that the cloud server 50 detects a changeof the setup value of the tenant open range and reports to change to themultifunction peripheral 10. The profile processing unit 15 of themultifunction peripheral 10 can delete the profile, in which the tenantID no more designated in the tenant open range is the administrationsource tenant ID. Therefore, it is always possible to cache the profilebeing highly probably used.

In a case where a priority is set to the tenant of the tenant openrange, the cloud server 50 can send the priority to the multifunctionperipheral 10 together with the profile. The multifunction peripheral 10caches the profile in a range permitted by the capacity of the memorydevice in an order having a higher priority. Even if there is a limit tothe profile to be cached, it is possible to cache from the profilehaving a higher probability to use.

In this case, if the priority of the tenant ID is changed, it ispreferable that the cloud server 50 reports the change of the priorityof the tenant ID. With this, the profile processing unit 15 of themultifunction peripheral 10 can appropriately change the profile cachedin response to the priority.

Fourth Embodiment

Within the first to third embodiments, there is provided the informationprocessing system 100, in which the profile used by oneself can be usedby the multifunction peripheral 10 inside the tenant. Even in a casewhere the tenant, in which the multifunction peripheral 10 isregistered, is different from the tenant, in which the user isregistered, the user can use the profile always used by the user afterthe user logs into from the multifunction peripheral 10.

However, in a case where the user selects the application requiring anindividual authentication (a login) by pushing and logs into themultifunction peripheral 10 of a tenant different from the tenant, inwhich the user is registered, there is an inconvenience that the screenreturns to the app home screen 501 even though the application hasalready been selected, and the user should push (step Select) the app tobe used again.

Description is given by referring to FIGS. 22A to 22C. FIGS. 22A to 22Care an example of explaining a screen transition at the time of thelogin.

(1) An app 3 is pushed by the user on the app home screen 501 (FIG. 22A)

(2) Because the app 3 is an app requiring a login by the user, themultifunction peripheral 10 displays the login screen 511 (FIG. 22B).

The app requiring the login is an app requiring information (the name orthe mail address) of the user who logs into or an app using a setup ofan individual.

(3) If the login is successful, the profile of the tenant, in which theuser is registered, is acquired. However, the type of the app providedby the tenant may probably differ. Therefore, the multifunctionperipheral 10 displays the app home screen 501 again based on theacquired profile.

Because of the above screen transition, the user is required to push theapp 2 (FIG. 22C illustrates app A, app B, app C, and app D, one of whichis the same as app 3) again. Therefore, there is an inconvenience thatthe operation becomes cumbersome.

Function

FIG. 23 is an example of a functional block diagram for explaining thefunction of the information processing system 100. Referring to FIG. 23,the structural elements having the same reference symbols as FIG. 7Aperform similar functions. Therefore, only major structural elements ofthe fourth embodiment may be described.

[[Multifunction Peripheral 10]]

The multifunction peripheral 10 includes a screen transition destinationcontrol unit 59 in comparison with FIG. 7A. The screen transitiondestination control unit 59 is implemented by the CPU 401 illustrated inFIG. 6 executing the program 408 p or the like to control a screendisplayed after the user logs into the multifunction peripheral 10.

Example of Screen Transition

FIG. 24 illustrates an example of a screen transition displayed by themultifunction peripheral 10 of the fourth embodiment. Referring to FIG.24, (a) illustrates an example of the app home screen 501. In one case,the user selects one of several apps, and in another case, the userpushes down the login button 502. Further, in the one case where theuser selects one of several apps, the login may be required or may notbe required depending on the selected one of the several apps.

When the login button 502 is pushed by the user, the login screen 511 in(b) of FIG. 24 is displayed. The login screen 511 is provided to input amail address and a password at a time when the user logs into themultifunction peripheral 10 (or the information processing system 100).

In a case where the user selects the app and the app requires the login,the login screen illustrated in (e) of FIG. 24 is displayed. The loginscreen 511 (a first screen) illustrated in (e) of FIG. 24 and the loginscreen 511 (the first screen) illustrated in (b) of FIG. 24 are thesame.

In a case where the user selects the app (the app 3 is selected as anexample) on the app home screen 501 and the app does not require thelogin, the app screen 521 before the login illustrated in (d) of FIG. 24is displayed. The app screen 521 includes a destination column 523, alogin button 522, and a start button 524. The app 3 is an app of aservice of “Scan To Cloud Storage” or “Print From Cloud Storage”. The“Scan To Cloud Storage” is the service (an app) of uploading an imageread by the multifunction peripheral 10 is uploaded to an individualstorage. The “Print From Cloud Storage” is the service (the app) ofdownloading a file from an individual storage in the cloud and printingin the multifunction peripheral 10. In the “Scan To Cloud Storage”, theuser inputs an upload destination storage (folder) in the userdestination column 523 and pushes down the start button 524.

When the user pushed the login button on the app screen 521 before thelogin illustrated in (d) of FIG. 24, the login screen 511 illustrated in(e) of FIG. 24 is displayed. In a case where the user selects the app(the app 3 is selected as the example) on the app home screen 501 andthe app 3 is used upon the login, the login screen 511 before the loginillustrated in (e) of FIG. 24 is displayed.

When the login is permitted on the login screen 511 illustrated in (b)of FIG. 24, the app home screen 501 after the login illustrated in (h)or (c) is displayed. In a case where the profile associated with themultifunction peripheral 10 b differs from the profile associated withthe user, the app home screen based on the profile associated with theuser is used. Therefore, the app home screen 501 ((h) of FIG. 24)different from that before the login is displayed. In a case where theprofile associated with the multifunction peripheral 10 b is the same asthe profile associated with the user, the app home screen 501 before thelogin illustrated in (c) of FIG. 24 is displayed without a changebecause the profile as the source of the app home screen does notchange.

In (c) and (h) of FIG. 24 after the login, a login person name 506 and alogout button 505 are displayed unlike (a) of FIG. 24. Because the apphome screen 501 illustrated in (h) of FIG. 24 is based on the profile ofthe tenant, in which the user is registered, the app home screen 501illustrated in (h) differs from that illustrated in (a) of FIG. 24.Because the app home screen 501 illustrated in (c) of FIG. 24 is basedon the profile of the tenant, in which the multifunction peripheral 10 bis registered, the app home screen 501 illustrated in (c) is the same asthat illustrated in (a) of FIG. 24. Further, because the login button ispushed in (a) of FIG. 24, the user does not select the app. Therefore,it is appropriate that the app home screen 501 is displayed again like(c) and (h) of FIG. 24.

In a case where the login is permitted on the login screen 511 of (e) ofFIG. 24, two screen transitions occur in response to the followingconditions: (1) No same app is present in the tenant of the logindestination: (c) and (h) of FIG. 24; and (2) A same app is present inthe tenant of the login destination: (f) of FIG. 24.

In case of (1), because no same app is present in the tenant of thelogin destination, the app home screen 501 is displayed. Is which of (c)and (h) displayed is as described above.

In case of (2), because the same app is present in the tenant of thelogin destination, the app screen 521 is displayed. The app screen 521after the login is illustrated in (f) of FIG. 24. In FIG. 24, because(f) is after the login, the login person name 526 and the logout button525 are displayed unlike (d) of FIG. 24. Because the user selects an appon the app home screen 501, the app needs not to be selected again afterthe app screen 521 illustrated in (f) of FIG. 24 is displayed.

Further, when the user causes the app home screen 501 to display on theapp home screen 501 after the login illustrated in (f) of FIG. 24 (forexample, a return button on the operation panel 411 is pushed), the apphome screen 501 after the login illustrated in (g) and (i) of FIG. 24 isdisplayed. In a case where the profile associated with the multifunctionperipheral 10 b differs from the profile associated with the user, theapp home screen based on the profile associated with the user is used.Therefore, the app home screen 501 ((g) of FIG. 24) different from thatbefore the login is displayed. In a case where the profile associatedwith the multifunction peripheral 10 b is the same as the profileassociated with the user, the app home screen 501 before the loginillustrated in (i) of FIG. 24 is displayed without a change because theprofile as the source of the app home screen does not change.

Because the app home screen 501 illustrated in (g) of FIG. 24 is basedon the profile of the tenant, in which the user is registered. Becausethe app home screen 501 illustrated in (i) of FIG. 24 is based on theprofile of the tenant, in which the multifunction peripheral 10 b isregistered, the app home screen 501 illustrated in (i) is the same asthat illustrated in (a) of FIG. 24.

As such, the information processing system 100 can change the screentransition according to the login, in which the user pushes down thelogin button 502 on the app home screen 501 illustrated in (a) of FIG.24, or the login after selecting the app. Specifically, in a case wherethe condition of is satisfied, the app screen 521 after the loginillustrated in (f) of FIG. 24 is displayed. Therefore, when the userselects the app, it is possible to display the app home screen 501 afterthe login without returning to the app home screen 501 for the user.

Operation Procedure

[[In a Case where the User of the Tenant A Pushes Down an App Held bythe Tenant, in which the Multifunction Peripheral 10 is Registered, toLog in the Tenant A, and the Same App is not Present in the Tenant A]]

FIG. 25 is an example of a sequence diagram illustrating a login to thecloud server 50 using the multifunction peripheral 10 of the tenant, inwhich the user is not registered, and the profile 9 of oneself is usedin the multifunction peripheral 10. Referring to FIG. 25, a differencefrom FIG. 8 is mainly described. Here, for convenience of explanation,the multifunction peripheral 10 is registered in the tenant B and theuser is registered in the tenant A. Because processes of step S1 to S14are the same as the processes in FIG. 25, the corresponding processesare omitted from FIG. 25.

The user conducts operations of inputting the user ID and the passwordto log in using the login screen 511 (step S21). At this time, there area case where the user logs into from the screen of the app and a casewhere the user logs into from the app home screen 501.

The multifunction peripheral 10 sends the user information, theapparatus information, and the app ID to the cloud server 50 (step S22to S24). The app ID is app identification information for specifying theapp as described above. This app ID indicates that to which app the appscreen 521 before the login screen 511 belongs. As illustrated in (a) ofFIG. 24, in a case where the login screen 511 is displayed in the apphome screen 501, the app ID indicates NULL (no app) or the app homescreen 501. In the explanation of FIG. 25, the app ID of any app may beincluded.

Subsequent processes of steps S25 to S34 may be similar to those in FIG.8. When the user logs in, the cloud server 50 determines the profilebased on the tenant, in which the multifunction peripheral 10 isregistered, and the tenant, in which the user is registered.

The profile determining unit 52 requests to send a transitiondestination screen to the screen transition destination control unit 59(S345). This request includes a profile and an app ID. This app ID isthe app ID of step S25.

The screen transition destination control unit 59 determines thetransition destination screen in the process illustrated in FIG. 27described below, and sends out the transition destination screen to theprofile determining unit 52 (step S346). Referring to FIG. 25, becausethe app held by the tenant B is not held by the tenant A, the transitiondestination screen is the app home screen 501 ((c) and (h) of FIG. 24).

Steps S35 to S38 are similar to FIG. 8. The profile of the tenant A, inwhich the login result and the user are registered, is sent to themultifunction peripheral 10.

The display processing unit 14 of the multifunction peripheral 10displays the app home screen 501 using the profile (step S39). Becausethe user operates the app screen 521 to be displayed at the login, theuser selects the app again.

[[In a Case where the User of the Tenant A Pushes Down the App Held bythe Tenant, in which the Multifunction Peripheral 10 is Registered, toLog in the Tenant A, and the Same App is Present in the Tenant A]]

FIG. 26 is an example of a sequence diagram illustrating a login to thecloud server 50 using the multifunction peripheral 10 of the tenant, inwhich oneself is not registered, and the profile 9 of oneself is used inthe multifunction peripheral 10. Referring to FIG. 26, a difference fromFIG. 25 is mainly described.

The screen transition destination control unit 59 determines thetransition destination screen in the process illustrated in FIG. 27described below, and sends out the transition destination screen to theprofile determining unit 52 (step S346). Referring to FIG. 26, becausethe tenant A holds the app held by the tenant B, the transitiondestination screen is the app screen 521.

Because the transition destination screen is the app screen 521, theprofile determining unit 52 designates the profile ID and the app IDfrom the profile administering unit 55 and acquires the app setup (stepS347). This is because the multifunction peripheral 10 does not displaythe app home screen 501 and therefore the profile is not yet necessary.Further, it is sufficient that the cloud server 50 sends an app setup ofan app selected by the user to the multifunction peripheral 10.Therefore, the transmission time can be decreased.

In a manner similar to FIG. 25, the login result and the app setup aresent to the multifunction peripheral 10 (S358, S368, S378, and S388).

The display processing unit 14 of the multifunction peripheral 10displays the app screen 521 ((f) of FIG. 24) of the app selected by theuser before the login using the app setup (step S398).

Next, the user displays the app home screen 501.

The user conducts an operation of displaying the app home screen 501 onthe multifunction peripheral 10 (step S1). The user conducts anoperation of displaying the app home screen 501 on the multifunctionperipheral 10 (step S1).

When the operation receiving unit 12 receives this operation, theoperation receiving unit 12 requests the communication unit 11 toacquire the profile 9 (step S42).

The communication unit 11 of the multifunction peripheral 10 sends theacquisition request to acquire the profile 9 to the cloud server 50(step S3). The acquisition request includes the apparatus information ofthe multifunction peripheral 10 and the tenant ID during the login.

When the communication unit 51 of the cloud server 50 receives theacquisition request to acquire the profile 9, the communication unit 51sends out the acquisition request to acquire the profile 9 to theprofile determining unit 52 (step S44).

The profile determining unit 52 designates the tenant ID and requeststhe profile administering unit 55 to send the profile ID correspondingto the tenant ID.

The profile administering unit 55 sends out the profile ID of theprofile designated by the tenant ID to the profile determining unit 52(step S46).

The profile determining unit 52 sends the profile 9 specified by theprofile ID to the profile administering unit 55 (step S47).

The profile administering unit 55 sends out the profile to the profiledetermining unit 52 (Step S48).

The profile determining unit 52 sends out the acquired profile 9 to thecommunication unit 51 (step S49).

The communication unit 51 of the cloud server 50 receives the profile 9and sends the profile 9 to the multifunction peripheral 10 (step S50).

The communication unit 11 of the multifunction peripheral 10 receivesthe profile 9 and sends out the profile 9 to the display processing unit14 (step S51).

The display processing unit 14 displays an app home screen 501 ((g) and(i) of FIG. 24) based on the profile 9 on the operation panel (stepS52).

The display processing unit 14 may start to acquire the profile 9 afterthe step S39 without an operation by the user after the step S39 and maycache the acquired profile 9 before the user operates to display the apphome screen 501 in the multifunction peripheral 10. The multifunctionperipheral 10 acquires the profile from the information processingapparatus during a display of the app screen 521 and caches the acquiredprofile. In this case, when the user operates to display the app homescreen 501, the app home screen 501 can be displayed using the cache soas to decrease a time for displaying the app home screen 501.

[[Determination of Profile]]

FIG. 27 is an example of a flow chart for explaining a procedure thatthe screen transition destination control unit 59 determines thetransition destination screen.

The screen transition destination control unit 59 refers to the app IDto determine whether the user displays the login screen 511 or the appscreen 521 is transited to the login screen 511 (step S410). Saiddifferently, in FIG. 24, it is determined whether (a) is transited to(d) or (e). Information whether the login is necessary to use the appinformation is set in the app information. The screen transitiondestination control unit 59 specifies the app information 302 using theapp ID and determines whether the login is necessary. In a case wherethe login is necessary, step S410 is determined to be YES.

In a case where step S410 is determined to be NO, the app home screen501 has been transited to the login screen 511 by the user. Therefore,the screen transition destination control unit 59 determines thetransition destination screen after the login to be app home screen 501illustrated in (c) or (h) of FIG. 24 (step S450).

In a case where step S410 is determined to be YES, the app screen 521has been transited to the login screen 511 by the user. Therefore, thescreen transition destination control unit 59 checks the app included inthe profile of the tenant, in which the user is registered (step S420).

The screen transition destination control unit 59 determines whether theapp of the app ID sent from the multifunction peripheral 10 is includedin the profile of the tenant, in which the user is registered (whetherthe profile of the tenant, in which the user is registered, has the sameapp ID) (step S430).

In a case where the determination of step S30 is YES, the multifunctionperipheral 10 can display the app screen 521 of the app selected by theuser. Therefore, the screen transition destination control unit 59determines the transition destination screen after the login to be theapp screen 521 illustrated in (f) of FIG. 24 (step S440).

In a case where the determination of step S30 is NO, the multifunctionperipheral 10 cannot display the app screen 521 of an app the same asthe app selected by the user. Therefore, the screen transitiondestination control unit 59 determines the transition destination screenafter the login to be the app home screen 501 illustrated in (c) and (h)of FIG. 24 (step S450).

As described above, in a case where the user selects the app requiringthe login in the information processing system, the app home screen 501is not displayed. Therefore, without pushing (selecting) the app to beused again, the user can use the app.

General Overview

As described above, the information processing system 100 of the fourthembodiment can operate the multifunction peripheral using the profile,which is ordinarily used by the user, even if the multifunctionperipheral 10, in which the user is not registered is used. Further, inthis case, it is possible to limit the app that the user uses. Further,because the cloud server 50 sends the difference profile, a drop of theperformance caused by the transmission can be prevented so as to preventthe performance from lowering.

Other Embodiments

For example, the cloud server 50 has been described to be present in theInternet, the cloud server 50 may be connected to the LAN, with whichthe multifunction peripheral 10 is connected.

Further, major functions are classified in the structural examplesillustrated in FIGS. 7A, 12, and 16 to facilitate understanding if theprocesses of the multifunction peripheral 10 and the cloud server 50.The present invention is not limited by a way of classifying into aprocessing unit and/or the name of the processing unit. The processes ofthe multifunction peripheral 10 and the cloud server 50 can be furtherclassified into more processing units. Further, the one processing unitcan be classified so as to include further more processes.

The operation receiving unit 12 is an example of a receiving unit. Thecommunication unit 11 is an example of a first communication unit.

The communication unit 51 is an example of a second communication unit.The profile determining unit 52 is an example of a setup informationdetermining unit. The app determining unit 56 is an example of afunction determining unit. The profile difference determining unit 58 isan example of a difference information producing unit. The profileprocessing unit 15 is an example of a setup information administeringunit. The screen transition destination control unit 59 is an example ofa transition destination screen control unit. The display processingunit 14 is an example of a display processing unit.

The present invention can be implemented in any convenient form, forexample using dedicated hardware, or a mixture of dedicated hardware andsoftware. The present invention may be implemented as computer softwareimplemented by one or more networked processing apparatuses. The networkcan comprise any conventional terrestrial or wireless communicationsnetwork, such as the Internet. The processing apparatuses can compromiseany suitably programmed apparatuses such as a general purpose computer,personal digital assistant, mobile telephone (step Such as a WAP or3G-compliant phone) and so on. Since the present invention can beimplemented as software, each and every aspect of the present inventionthus encompasses computer software implementable on a programmabledevice.

The computer software can be provided to the programmable device usingany storage medium for storing processor readable code such as a floppydisk, hard disk, CD ROM, magnetic tape device or solid state memorydevice.)

The hardware platform includes any desired kind of hardware resourcesincluding, for example, a central processing unit (CPU), a random accessmemory (RAM), and a hard disk drive (HDD). The CPU may be implemented byany desired kind of any desired number of processor. The RAM may beimplemented by any desired kind of volatile or non-volatile memory. TheHDD may be implemented by any desired kind of non-volatile memorycapable of storing a large amount of data. The hardware resources mayadditionally include an input device, an output device, or a networkdevice, depending on the type of the apparatus. Alternatively, the HDDmay be provided outside of the apparatus as long as the HDD isaccessible. In this example, the CPU, such as a cache memory of the CPU,and the RAM may function as a physical memory or a primary memory of theapparatus, while the HDD may function as a secondary memory of theapparatus.

All examples and conditional language recited herein are intended forpedagogical purposes to aid the reader in understanding the principlesof the invention and the concepts contributed by the inventor tofurthering the art, and are to be construed as being without limitationto such specifically recited examples and conditions, nor does theorganization of such examples in the specification relate to a showingof the superiority or and inferiority of the invention. Although theinformation processing system has been described in detail, it should beunderstood that various changes, substitutions, and alterations could bemade thereto without departing from the spirit and scope of theinvention.

This application is based upon and claims the benefit of priority of theprior Japanese Patent Application No. 2016-205228, filed on Oct. 19,2016, and the Japanese Patent Application No. 2017-091432, filed on May1, 2017, the entire contents of which are incorporated herein byreference.

What is claimed is:
 1. An information processing system in which setupinformation related to a setup of an apparatus is sent to the apparatus,the information processing system comprising: the apparatus, theapparatus including a first processor, and a first memory storing firstprogram instructions that cause the first processor to: receive userinformation of a user of the apparatus, the user information includinguser identification information that specifies the user, and send thereceived user information and apparatus information to an informationprocessing apparatus, the apparatus information including apparatusidentification information that specifies the apparatus; and theinformation processing apparatus, the information processing apparatusincluding a second processor, and a second memory storing second programinstructions that cause the second processor to: receive the userinformation and the apparatus information, and determine the setupinformation of the apparatus to be sent to the apparatus used by theuser, based on the received apparatus information and the userinformation, and send the determined setup information to the apparatus,wherein the second memory further stores the apparatus information inassociation with group identification information that specifies a groupusing a resource of the information processing system, and the userinformation in association with the group identification informationthat specifies the group to which the user belongs, and the secondprocessor refers to the second memory to determine whether the groupidentification information associated with the apparatus information isthe same as the group identification information associated with theuser information, wherein in a case where the group specified by thegroup identification information associated with the apparatusinformation is the same as the group specified by the groupidentification information associated with the user information, thesecond processor sends the setup information specified by the groupidentification information associated with the user information, and ina case where the group specified by the group identification informationassociated with the apparatus information is different from the groupspecified by the group identification information associated with theuser information, the second processor further refers to first requestpermission information, in which the group identification information ofone or more permitted groups from among other groups different from thegroup, the group identification information of the permitted groupsbeing permitted to request information related to the group beingregistered in association with the group identification informationassociated with the apparatus, determines whether the group specified bythe group identification information associated with the userinformation is included among the one or more permitted groupsassociated with the group specified by the group identificationinformation associated with the apparatus, and sends the setupinformation specified by the group identification information associatedwith the user to the apparatus in a case where the first requestpermission information indicates that the group specified in the groupidentification information associated with the user is included amongthe permitted groups associated with the group specified by the groupidentification information associated with the apparatus information. 2.The information processing system according to claim 1, wherein, in acase where the group specified by the group identification informationassociated with the apparatus information is different from the groupspecified by the group identification information associated with theuser information, the second processor refers to the first requestpermission information to determine whether the group specified by thegroup identification information associated with the user information inincluded among the permitted groups associated with the group specifiedby the group identification information associated with the apparatusinformation, such that in a case where the second processor determinesthat the group specified by the group identification informationassociated with the user information is not included among the permittedgroups, the second processor determines that the setup informationspecified by the group identification information associated with theapparatus information is to be sent to the apparatus, and in a casewhere the second processor determines that the group specified by thegroup identification information associated with the user information isincluded among the permitted groups second processor then further refersto second request permission information in which the groupidentification information of the another group, to which the group canprovide the information in association with the group identificationinformation, determines whether the group specified by the groupidentification information associated with the user information isincluded among the permitted groups, and sends the setup informationspecified by the group identification information associated with theuser information in the case where the group specified by the groupidentification information associated with the user information isincluded among the permitted groups.
 3. The information processingsystem according to claim 1, wherein the second program instructionsfurther cause the second processor to: determine that the setupinformation specified by the group identification information associatedwith the user information is to be sent to the apparatus regardless ofwhether the group specified by the group identification informationassociated with the apparatus information is the same as the groupspecified by the group identification information associated with theuser information.
 4. The information processing system according toclaim 1, wherein, the second program instructions further cause thesecond processor to: determine a function of the apparatus included inthe setup information sent to the apparatus based on whether the groupspecified by the group identification information associated with theapparatus information is the same as the group specified by the groupidentification information associated with the user information.
 5. Theinformation processing system according to claim 4, wherein the secondmemory further stores first permission function information thatindicates the function of the apparatus permitted by the group specifiedby the group information associated with the apparatus information, andthe second program instructions further cause the second processor to:refer to the first permission function information, and omit anyfunction other than the permitted function indicated by the firstpermission function information in a case where the group specified bythe group identification information associated with the apparatusinformation is different from the group specified by the groupidentification information associated with the user information.
 6. Theinformation processing system according to claim 4, wherein the secondmemory further stores second permission function information thatindicates the function of the apparatus permitted by the group specifiedby the group information associated with the user information, and thesecond program instructions further cause the second processor to: referto the second permission function information, and omit any functionother than the permitted function indicated by the second permissionfunction information in a case where the group specified by the groupidentification information associated with the apparatus information isdifferent from the group specified by the group identificationinformation associated with the user information.
 7. The informationprocessing system according to claim 4, wherein, the second memoryfurther stores first permission function information that indicates thefunction of the apparatus permitted by the group specified by the groupinformation associated with the apparatus information, and secondpermission function information that indicates the function of theapparatus permitted by the group specified by the group informationassociated with the user information; and the second programinstructions further cause the second processor to: refer to the firstpermission function information, refer to the second permission functioninformation, and omit any function other than the permitted functionsindicated by the first permission function information and the secondpermission function information in a case where the group specified bythe group identification information associated with the apparatusinformation is different from the group specified by the groupidentification information associated with the user information.
 8. Theinformation processing system according to claim 5, wherein the groupidentification information associated with the apparatus information andthe group identification information associated with the userinformation further include detailed function permission informationindicating a detailed function, which is necessary for providingdetailed function is predetermined for each function of the apparatus,permitted by the group specified by the group identification informationassociated with the apparatus information and by the group specified bythe group identification information associated with the userinformation, respectively, and the second processor omits any functionrequiring any detailed function other than the detailed functionindicated by the detailed function permission information included inthe group identification information associated with the apparatusinformation and in the group identification information associated withthe user information.
 9. The information processing system according toclaim 5, wherein the second processor, in a case where the groupspecified by the group identification information associated with theapparatus information and the group specified by the groupidentification information associated with the user information is thesame, omits the function other than the detailed function permitted bythe group specified by the group identification information associatedwith the apparatus information from the setup information.
 10. Theinformation processing system according to claim 1, wherein the secondprogram instructions further cause the second processor to: generate thesetup information specified by the group identification informationassociated with the apparatus information and difference information ofthe setup information specified by the group identification informationassociated with the user information, and send the generated differenceinformation in place of the setup information.
 11. The informationprocessing system according to claim 10, wherein the first processor:receives the difference information, and combines first setupinformation of the group, in which the apparatus previously held isregistered, with the difference information to generate second setupinformation of the group, in which the user is registered.
 12. Theinformation processing system according to claim 11, wherein the firstprogram instructions further cause the first processor to: operate theapparatus using the second setup information while holding the firstsetup information, and operate the apparatus using the first setupinformation, in a case where the user logs out.
 13. The informationprocessing system according to claim 11, wherein first programinstructions further cause the first processor to: hold partialinformation of the first setup information and the differenceinformation, the partial information being not used in the second setupinformation, and acquire the partial information of the first setupinformation used by the second setup information from the second setupinformation based on the difference information and combine the partialinformation of the first setup information with the held first setupinformation to restore the first setup information.
 14. The informationprocessing system according to claim 12, wherein first programinstructions further cause the first processor to: delete the secondsetup information upon the user logging out.
 15. The informationprocessing system according to claim 12, wherein first programinstructions further cause the first processor to: refrain from deletingthe second setup information until a number of logouts of the userreaches a predetermined number, and delete older second setupinformation in a case where the number of logouts of the user reachesthe predetermined number.
 16. The information processing systemaccording to claim 12, wherein first program instructions further causethe first processor to: refrain from deleting the second setupinformation of the group permitted to access by the group, in which theapparatus is registered, and holds in the case where the user logs out.17. An information processing apparatus that sends setup informationrelated to a setup of an apparatus to the apparatus, the informationprocessing apparatus comprising: a first processor, and a first memorystoring first program instructions that cause the first processor to:receive user information of the apparatus and apparatus informationrelated to the apparatus, the user information including useridentification information that specifies the user, and the apparatusinformation including apparatus identification information thatspecifies the apparatus; determine the setup information of theapparatus to be sent to the apparatus used by the user, based on thereceived apparatus information and the user information, and send thedetermined setup information to the apparatus, wherein the memoryfurther stores the apparatus information in association with groupidentification information that specifies a group using a resource ofthe information processing system, and the user information inassociation with the group identification information that specifies thegroup to which the user belongs, and the processor refers to the memoryto determine whether the group identification information associatedwith the apparatus information is the same as the group identificationinformation associated with the user information, wherein in a casewhere the group specified by the group identification informationassociated with the apparatus information is the same as the groupspecified by the group identification information associated with theuser information, the processor sends the setup information specified bythe group identification information associated with the userinformation, and in a case where the group specified by the groupidentification information associated with the apparatus information isdifferent from the group specified by the group identificationinformation associated with the user information, the processor furtherrefers to first request permission information, in which the groupidentification information of one or more permitted groups from amongother groups different from the group, the group identificationinformation of the permitted groups being permitted to requestinformation related to the group being registered in association withthe group identification information associated with the apparatus,determines whether the group specified by the group identificationinformation associated with the user information is included among theone or more permitted groups associated with the group specified by thegroup identification information associated with the apparatus, andsends the setup information specified by the group identificationinformation associated with the user to the apparatus in a case wherethe first request permission information indicates that the groupspecified in the group identification information associated with theuser is included among the permitted groups associated with the groupspecified by the group identification information associated with theapparatus information.
 18. A non-transitory computer-readable storagemedium storing a program for causing a computer to implement aninformation processing apparatus sending setup information related to asetup of an apparatus to the apparatus, information processing apparatuscomprising: a first processor, and a first memory storing first programinstructions that cause the first processor to: receive user informationof the apparatus and apparatus information related to the apparatus, theuser information including user identification information thatspecifies the user, and the apparatus information including apparatusidentification information that specifies the apparatus; determine thesetup information of the apparatus to be sent to the apparatus used bythe user, based on the received apparatus information and the userinformation, and send the determined setup information to the apparatus,wherein the memory further stores the apparatus information inassociation with group identification information that specifies a groupusing a resource of the information processing system, and the userinformation in association with the group identification informationthat specifies the group to which the user belongs, and the processorrefers to the memory to determine whether the group identificationinformation associated with the apparatus information is the same as thegroup identification information associated with the user information,wherein in a case where the group specified by the group identificationinformation associated with the apparatus information is the same as thegroup specified by the group identification information associated withthe user information, the processor sends the setup informationspecified by the group identification information associated with theuser information, and in a case where the group specified by the groupidentification information associated with the apparatus information isdifferent from the group specified by the group identificationinformation associated with the user information, the processor furtherrefers to first request permission information, in which the groupidentification information of one or more permitted groups from amongother groups different from the group, the group identificationinformation of the permitted groups being permitted to requestinformation related to the group being registered in association withthe group identification information associated with the apparatus,determines whether the group specified by the group identificationinformation associated with the user information is included among theone or more permitted groups associated with the group specified by thegroup identification information associated with the apparatus, andsends the setup information specified by the group identificationinformation associated with the user to the apparatus in a case wherethe first request permission information indicates that the groupspecified in the group identification information associated with theuser is included among the permitted groups associated with the groupspecified by the group identification information associated with theapparatus information.